src/features/mirrors/components/MirrorDetails/MirrorDetails.test.tsx:51

• This file contains two identical test cases named "displays preserve signatures status" with the same assertions. Keeping both adds redundant runtime and makes future failures harder to interpret; consider removing one or changing the second to cover the opposite value (e.g. preserveSignatures=false => "No").

  it("displays preserve signatures status", async () => {
    const mirrorWithPreserveSignatures = mirrors.find(
      ({ preserveSignatures }) => preserveSignatures,
    );

src/features/mirrors/components/MirrorDetails/MirrorDetails.test.tsx:45

• This test renders mirrorWithPreserveSignatures (the first mock with preserveSignatures=true), but then asserts the heading for mirrors[0].displayName. With the current mocks, mirrorWithPreserveSignatures is mirrors[1], so this assertion will fail. Assert against mirrorWithPreserveSignatures.displayName instead.

  it("displays preserve signatures status", async () => {
    const mirrorWithPreserveSignatures = mirrors.find(
      ({ preserveSignatures }) => preserveSignatures,
    );

    assert(mirrorWithPreserveSignatures);

    renderWithProviders(
      <Suspense fallback={<LoadingState />}>
        <MirrorDetails />
      </Suspense>,
      undefined,
      `?name=${mirrorWithPreserveSignatures.name}`,
    );

    await expectLoadingState();

    expect(
      screen.getByRole("heading", { name: mirrors[0].displayName }),
    ).toBeInTheDocument();

src/features/mirrors/components/AddMirrorForm/AddMirrorForm.test.tsx:90

• This no longer verifies the snapshot-specific payload. Because the MSW create handler accepts any body and always succeeds, the test would pass even if the form stopped appending the selected snapshot date to archiveRoot.

    await user.click(screen.getByRole("button", { name: "Add mirror" }));

    expect(
      await screen.findByText("You have successfully added Name."),
    ).toBeInTheDocument();

src/features/mirrors/components/AddMirrorForm/AddMirrorForm.test.tsx:169

• This test fills several third-party mirror fields but only asserts the generic success notification. Since the create handler does not validate the body, regressions in archiveRoot, distribution, components, architectures, or gpgKey serialization would not fail the test anymore.

    await user.click(screen.getByRole("button", { name: "Add mirror" }));

    expect(
      await screen.findByText("You have successfully added Name."),
    ).toBeInTheDocument();

src/features/mirrors/components/EditMirrorForm/EditMirrorForm.test.tsx:195

• This test toggles the download options but only verifies the success notification. Because the update handler does not validate the request body, the test would still pass if downloadUdebs, downloadSources, or downloadInstaller stopped being sent correctly.

    expect(
      await screen.findByText(
        `You have successfully edited ${mirror.displayName}.`,
      ),
    ).toBeInTheDocument();

src/features/mirrors/components/AddMirrorForm/AddMirrorForm.test.tsx:115

• The preserve-signatures behavior is no longer asserted after submission. The current success-notification check would still pass if preserveSignatures were omitted or sent as false, because the MSW handler does not validate the request body.

    await user.click(screen.getByRole("button", { name: "Add mirror" }));

    expect(
      await screen.findByText("You have successfully added Name."),
    ).toBeInTheDocument();

src/features/mirrors/components/EditMirrorForm/EditMirrorForm.test.tsx:118

• The previous payload assertion ensured that keeping the current key did not send a gpgKey update. Replacing it with a success-notification check leaves that behavior uncovered, because the MSW handler will succeed even if the form accidentally clears or replaces the key.

    await user.click(screen.getByRole("button", { name: "Save changes" }));

    expect(
      await screen.findByText(
        `You have successfully edited ${mirror.displayName}.`,